Data Groups
With few exceptions, data groups must be defined in a device template file (DTF) in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.
CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.
For information about data group definitions and device template files, see Device Template Files.
For more information about data group dependencies, see Data Group Dependencies.
Notes:
-
When point processing is performed on history data groups, only closed records will be published and processed to points. If a device has leading timestamped records and returns the current, open record, point processing will not be performed for that record, even though there is data in the DDS transaction. The point record will be updated only when that record is closed. This is to avoid a situation where a point has multiple entries with the same timestamp, since an open record may be still updating values with each new poll, but each update will have the same timestamp. For example, say you start polling for a daily history record at 8:00am, you’ll get the first value at 8:00am, then if you poll every five minutes, you’ll get new values throughout the day at the exact same timestamp. A history record is basically an array of data with a timestamp and values where the values have different process variables for each incremental poll. The timestamp won’t get written until the record is closed, which happens at the end of the time period, in this case, a day.
- Best practice recommends that you do not perform UDC and point processing on FMS data groups. The DEIDs specified in FMS data groups are generic and use the eFMS enumeration to identify the CygNet-defined FMS items referenced in the device template file. No polling is done on these data groups — all data is coming from the native data groups. Points should be mapped to the native data groups since that is the data group that is actually processing the device data. While point processing may work on the FMS data groups, it is not supported, not tested, not consistent across EIEs, and is not recommended practice.
Modbus Realflo EIE Data Groups
Browse by letter: [A] [B] [C] [D] [E] [F] [G] [H] [I] [L] [M] [N] [P] [S] [V]
| Data Group Type | Usage Notes |
|---|---|
|
"AGA-3 Config" provides AGA-3 (1985 and 1992) input data. |
|
|
Aga7Cfg |
"AGA-7 Config" provides AGA-7 input data. |
|
"AGA-8 GQ Data" |
|
|
"Batch Status - Gas" |
|
|
BatStatL |
"Batch Status - Liquid" |
|
BatStatW |
"Batch Status - Water" |
|
The "Configurable Data Group" data group provides a flexible way to create custom data groups on a per-device basis. See Configurable Data Group. |
|
|
Composite Data Group |
The "Composite Data Group" is a special kind of data group that enables you to combine any data group element(s) from any data group(s) as long as they are in the same template as the composite data group. The "Composite Data Group" does not appear in a remote device editor unless it has been defined in the relevant device template file. See Composite Data Group. |
|
CoriolCfg |
"Coriolis Meter Config" implements this set of registers. |
|
"Data Logger" allows a set of registers to be captured on a set time interval and retrieved at later time. It enables you to add up to 16 instantiations, each including its own set of up to eight log items. You do not need to instantiate DataLogCfg in order to use DataLog. Poll DataLog to acquire its associated configuration. DataLog includes a specialized device template file attribute called purgeData that enables you to purge read records from an associated field device. Note: If UDCs are defined for items in the data log, and history reporting is configured, points will be updated according to the history point data model. That is, for each record, all items will post to the VHS along with the point update time included in that record. In the CVS only, the point entry will reflect the most recent entry received. |
|
|
DataLogCfg |
"Data Logger Config" provides a grid view of DataLog configuration. You do not need to instantiate DataLogCfg in order to use DataLog. Poll DataLog to acquire its associated configuration. |
|
"Date and Time" |
|
|
"History - Daily" |
|
|
"Enron Events" Note: When changing the transaction retention settings for this data group type, you will be prompted to confirm the change. CygNet recommends that data be retained for at least 40 days to be available for CygNet Measurement. Either change the transaction retention settings to retain more data, or accept the settings, which may cause CygNet to lose data that cannot be retrieved again. |
|
|
"Event Def" defines the event-to-register mappings for relevant Realflo events. Its device template file definitions enable you to specify descriptive text and applicable units. This data group is required in support of FmsEvent. |
|
|
EventDefS |
"Event Def System" |
|
ExStatus |
"Read Exception Status" |
|
"Flow Computer ID" |
|
|
FlwRunCfg |
"Flow Run Config" provides contract input data and batch input data. |
|
FlwRunEx |
"Flow Run Execution State" |
|
FlwRunStat |
"Flow Run Status (v6.92.1)" |
|
FlwRunSt2 |
"Flow Run Status (v6.93.2)" |
|
"FMS Alarms" This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"FMS Batch" See FMS Batch Data Group. |
|
|
FmsConfig |
"FMS Configuration" must be retrieved before polling other FMS data groups of the same ordinal. This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
"FMS Events" This data group depends on supporting data groups to be defined in order for successful transactions to be completed. Dependencies |
|
|
"FMS Daily PM History" retrieves history data for gas, liquid and water meters. This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"FMS Hourly PM History" retrieves history data for gas, liquid and water meters. This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"FMS Hourly PQ History" This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
FmsProduct |
"FMS Liquid Product" enables the retrieval of liquid product data by an associated CygNet Measurement system. |
|
"Gas Quality" provides AGA-8 input data. |
|
|
GasChrom |
"Gas Chromatograph Config" |
|
GasStream |
"Gas Stream Config" |
|
"History - Batch Gas" |
|
|
"History - Batch Liquid" |
|
|
"History - Batch Water" |
|
|
"History - Daily" |
|
|
"History - Daily Liquid" |
|
|
"History - Daily Water" |
|
|
"History - Gas Quality" |
|
|
"History - Hourly" |
|
|
"History - Hourly Liquid" |
|
|
"History - Hourly Water" |
|
|
HistIdx |
"History Support (Index)" |
|
HistIdxB |
"History Index Batch" Realflo v6.92+ field devices provide a meter-specific method of retrieving historical data, which improves retrieval performance. Such a field device must be configured to retrieve data using the new method. If you upgrade to CygNet SCADA v8.2.0 or later and do not change the configuration of your Realflo field devices, you continue to retrieve historical data using the old method. If you upgrade to CygNet SCADA v8.2.0 or later and change the configuration of your Realflo v6.92 or later field devices to use the new method, you must also make modifications to applicable CygNet SCADA remote devices. At the least, delete all instantiations of the "History Support (Index)" (HistIdx) data group and replace it with "History Index Batch" (HistIdxB), "History Index Daily" (HistIdxD), and/or "History Index Hourly" (HistIdxH) instantiations that correlate with existing batch, daily, and hourly history data groups, like "History - Hourly Gas" (HistHry). |
|
HistIdxD |
"History Index Daily" Realflo v6.92 or later field devices provide a meter-specific method of retrieving historical data, which improves retrieval performance. Such a field device must be configured to retrieve data using the new method. If you upgrade to CygNet SCADA v8.2.0 or later and do not change the configuration of your Realflo field devices, you continue to retrieve historical data using the old method. If you upgrade to CygNet SCADA v8.2.0 or later and change the configuration of your Realflo v6.92 or later field devices to use the new method, you must also make modifications to applicable CygNet SCADA remote devices. At the least, delete all instantiations of the "History Support (Index)" (HistIdx) data group and replace it with "History Index Batch" (HistIdxB), "History Index Daily" (HistIdxD), and/or "History Index Hourly" (HistIdxH) instantiations that correlate with existing batch, daily, and hourly history data groups, like "History - Hourly Gas" (HistHry). |
|
HistIdxH |
"History Index Hourly" Realflo v6.92 or later field devices provide a meter-specific method of retrieving historical data, which improves retrieval performance. Such a field device must be configured to retrieve data using the new method. If you upgrade to CygNet SCADA v8.2.0 or later and do not change the configuration of your Realflo field devices, you continue to retrieve historical data using the old method. If you upgrade to CygNet SCADA v8.2.0 or later and change the configuration of your Realflo v6.92 or later field devices to use the new method, you must also make modifications to applicable CygNet SCADA remote devices. At the least, delete all instantiations of the "History Support (Index)" (HistIdx) data group and replace it with "History Index Batch" (HistIdxB), "History Index Daily" (HistIdxD), and/or "History Index Hourly" (HistIdxH) instantiations that correlate with existing batch, daily, and hourly history data groups, like "History - Hourly Gas" (HistHry). |
|
"History - Hourly" |
|
|
"Input Config - Density" provides density input data. |
|
|
InDpCfg |
"Input Config - DP" provides differential pressure input data. |
|
InMassCfg |
"Input Config - Mass" provides mass flow input data. |
|
InPulseCfg |
"Input Config - Pulse" provides turbine or pulse input data, as well as mass and volume data. |
|
InSpCfg |
"Input Config - SP" provides static pressure input data. |
|
InTempCfg |
"Input Config - Temp" provides temperature input data. |
|
InVolCfg |
"Input Config - Vol" provides volume flow input data. |
|
InWCutCfg |
"Input Config - Water Cut" provides water cut input data. |
|
"Flow Run Config - Liquid" provides liquid and water input data. |
|
|
"Meter Run ID" |
|
|
"Meter Run Units" must be instantiated and polled before any data group that relies on a configurable unit set can be polled. The ordinals of the unit set data group and its corresponding "Meter Run Units" data group must match. See Editing a Template. |
|
|
MVTCfg |
"MVT Config" |
|
MVTData |
"MVT Data" |
|
MVTRng |
"MVT Range Limits" |
|
"NX-19 Config" provides NX-19 input data. |
|
|
"Program Information" |
|
|
"Single Coil" See Single-Element Data Group. |
|
|
"Single Coil - Realflo Addr" See Single-Element Data Group. |
|
|
"Single 2-Byte Reg" See Single-Element Data Group. |
|
|
"Single 4-Byte Reg" See Single-Element Data Group. |
|
|
"Single 2-Byte Reg - Realflo Addr" See Single-Element Data Group. |
|
|
"Single 4-Byte Reg - Realflo Addr" See Single-Element Data Group. |
|
|
Station |
"Station Data" |
|
"Status Data" |
|
|
"V-Cone Config" provides V-cone input data. |
